Internet Info 1994 March/Internet Info CD-ROM (Walnut Creek) (March 1994).iso/inet/ietf/tnfs/tnfs-minutes-92jul.txt

Text File | 1993-02-17 | 5KB | 142 lines

Editor's Note: Minutes received 8/05

CURRENT_MEETING_REPORT_


Reported by Fred Glover/DEC

Minutes of the Trusted Network File Systems Working Group (TNFS)

The TNFS Working Group met for three sessions during the IETF July
meeting.  We:


   o Presented an overview and status of the TNFS Working Group during
     the first session for those participating for the first time.
   o Reviewed the final modifications to the TNFS document
     (TNFS-001.2.02) during the second session.
   o Reviewed implementation status and issues during the third session.


In addition, Fred presented an overview of the TNFS Working Group
achievements and current status during the Thursday afternoon IETF
plenary.

TNFS Working Group Status and Summary

During the first TNFS session, Fred presented an overview of the TNFS
Working Group effort, current status, and current set of documentation.
Dave Borman, our Area Director, was present, and helped us position our
documents.  We are presenting the TNFS document as a candidate for
proposed standard RFC. We will plan to present the token mapping
document as a (new) prototype RFC, and the implementation and
administrative documents as informational RFCs.  The other TNFS Working
Group documents, (interoperability test plan, tnfs.h, ...)  will not be
submitted as RFCs, but will continue to be maintained within the TNFS
archive.

TNFS Document Review

The IETF TNFS document has been available for comments in the IETF Draft
directory and TNFS archive since July, 1991.  During the July meeting,
the TNFS Working Group reviewed the current TNFS document for any final
edits prior to requesting the transition of its status to proposed RFC
draft:


   o We agreed to add one additional flag to the access protocol
     operation, STAT, which would request permission to ``stat'' the
     requested file.  Since the full set of attributes are returned with
     most all procedure calls, there is a question of which attributes a
     given client should be able to see from the set of cached
     attributes.  By adding STAT to our access procedure, and by
     maintaining per process cached attributes, the client will be able

                                   1





     to present an appropriate set of attributes to a requesting
     application from the cache.
   o We agreed to change the name of the SETLABEL procedure to the
     SETNAMELABEL procedure.  This new procedure name reflects the
     intended use of the procedure (i.e., to modify the label of the
     file name only; the SETATTR procedure is used to modify the label
     of the file).


The document will be updated to reflect these changes, and will be
placed in both the TNFS archive and IETF draft directory.  Fred will
then contact our IETF Area Director, Dave Borman, to indicate that the
document is ready to be reviewed for transition to RFC Proposed Standard
status.

Implementation Status, Issues

The Working Group reviewed the progress of current implementation
efforts.  One implementation now conforms to the current TNFS
specification, and several others are very close.  We reviewed TNFS test
plan, and discussed several upcoming opportunities for interoperability
testing:


   o The September TSIG meeting hosted by Cray Research:  this may be
     too early; we will ``poll'' via email during late August to
     determine if this is a possibility.
   o A November west coast site:  Carl Smith and Fred Glover will
     investigate possible test sites; November was identified as a more
     realistic timeframe for the completion of the other TNFS
     implementations.
   o The 1993 Connectathon:  no date exists for this at present, but
     this event is usually held during February or March; many of the
     TNFS Working Group member's companies already participate in
     Connectathon, so this is another good possibility.
   o The spring TSIG meeting:  it would be convenient from a testing
     perspective if this meeting were held during/near the time of
     Connectathon, but this would still be a good possibility with
     respect to timeframe.


Interoperability testing is an important milestone in supporting our
goal to promote the TNFS specification to Draft Standard.  Our test
plan, a documented set of ``non-mapped'' security attributes for
testing, and an update of the tnfs.h file, describing all of the TNFS
procedures and data structures are available in the TSIG/IETF archive to
facilitate the development of additional implementations.

Next Meeting


                                   2





Since the TNFS document is now being proposed for promotion to Proposed
Standard, the TNFS Working Group will plan to meet next in conjunction
with our interoperability testing.  This date will be identified via
email.  We will plan to review updates of the TKM specification,
implementation guide, and administrative guide via email.

Attendees

David Borman             [e-mail]
Fran Fadden              [e-mail]
Owen Gallagher           [e-mail]
Fred Glover              [e-mail]
Andy Lai                 [e-mail]
Sharon Lewis             [e-mail]
William Middlecamp       [e-mail]
Richard Newton           [e-mail]
Sam Nicholson            [e-mail]
Carl Smith               [e-mail]
Thomas Talpey            [e-mail]
Charles Watt             [e-mail]



                                   3